docs: add JSX rule about function references as children #7908
Conversation
Adds documentation explaining the common mistake of passing function references as JSX children instead of calling them. Includes examples showing incorrect and correct usage. Addresses facebook/react#34007
|
Hi @elkanatum! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Summary
Adds documentation explaining the common mistake of passing function references as JSX children instead of calling them.
Changes
writing-markup-with-jsx.mdType of Change
This addresses a common beginner mistake where developers accidentally pass function references as JSX children, resulting in
[Function]being displayed instead of meaningful content.Related Issue
Addresses facebook/react#34007